Product documentation
Preventive & Planned Maintenance in HSO Service Management supports the preparation, forecasting and execution of scheduled service activities. Maintenance can be based on contractual obligations, calendar frequencies, predefined intervals or equipment usage. The process converts maintenance requirements into planned visits and, when required, into Service Calls and Service Tasks.
Introduction
Preventive Maintenance is used to perform inspections, servicing, calibration and replacement activities before equipment failure occurs. It is commonly driven by Service Contracts, which define the maintenance obligations for covered Service Objects. Planned Maintenance can also be used outside a contract for service campaigns, recalls or other activities involving selected Service Objects.
Maintenance process
The maintenance process consists of defining the Service Schedule, selecting the relevant Service Objects, generating a visit forecast and converting planned visits into operational work. The Event Code identifies the maintenance activity and determines the work package associated with the Service Task. When maintenance is contract-driven, the contract also provides the applicable coverage and financial conditions.
Maintenance methods
HSO Service Management supports Frequency-Based and Interval-Based Maintenance. Frequency-Based Maintenance can use static or dynamic scheduling, while Meter-Driven Maintenance extends dynamic frequency scheduling by considering equipment usage. The appropriate approach depends on whether maintenance follows a fixed calendar pattern, defined lifecycle intervals or actual equipment usage.
Introduction
Service Schedules define the maintenance pattern applied to Service Objects. They determine which activities must be performed and the frequency or conditions under which maintenance visits are generated. A Service Schedule must be linked to the relevant Object Types before it can be selected for those objects.
Schedule content
A Service Schedule contains the maintenance activities represented by Event Codes and their scheduling rules. The Event Code and Object Type combination determines the associated work package, including estimated duration, materials, Service Operations and resource requirements.
Schedule selection
Service Schedules can be selected when preparing contract Visit Schedules or other planned maintenance activities. The selected schedule must be appropriate for the Service Object and its maintenance requirements. The resulting forecast should be reviewed before the planned visits are confirmed or converted into Service Calls.
Introduction
Frequency-Based Maintenance generates planned visits according to a recurring calendar pattern. It is suitable for activities such as monthly inspections, quarterly servicing or annual maintenance, where the required frequency is defined independently of actual equipment usage.
Maintenance frequency
A frequency schedule defines how often particular maintenance activities must occur within a period. Multiple Event Codes can be included, each with its own frequency. For example, a Service Object may require quarterly inspections and an annual major service.
Visit distribution
When the maintenance forecast is generated, the system distributes the required visits across the applicable period. Where maintenance activities overlap, the configured schedule can determine whether a more extensive service replaces another planned activity to avoid duplicate visits.
Static and dynamic scheduling
Frequency-Based Maintenance can follow a static or dynamic planning approach. With static scheduling, the original maintenance pattern remains the reference for future visits. With dynamic scheduling, future visits are recalculated based on the actual realization date of the preceding maintenance visit.
Planning considerations
Forecasted dates are subject to the applicable scheduling conditions, including calendars, permitted visit days and visit margins. The planner should review the resulting dates before generating operational work.
Introduction
Interval-Based Maintenance generates visits according to defined intervals or lifecycle milestones rather than an evenly distributed calendar frequency. It supports maintenance patterns in which different activities must occur at different stages of a Service Object's lifecycle.
Interval definitions
Intervals can represent elapsed time, object age, usage or counter-based milestones. For example, a Service Object may require an initial inspection after one month, a second inspection after six months and a major service after two years. Depending on the schedule, the sequence can repeat or end after the defined maintenance cycle.
Object information
Interval calculations depend on the relevant Service Object information, such as installation date, starting counter value or estimated usage. Incorrect or incomplete object information can affect the calculated visit dates.
Visit forecasting
The maintenance forecast translates the configured intervals into planned visits. The first calculated visit should be reviewed carefully because subsequent visits may depend on the same starting point or maintenance sequence.
Introduction
Dynamic Maintenance is a scheduling option within Frequency-Based Maintenance. Instead of retaining the original planned dates, it recalculates future maintenance visits based on the actual realization date of the preceding visit.
Dynamic recalculation
When a maintenance visit is completed earlier or later than planned, the remaining visits are recalculated accordingly. For example, if maintenance is scheduled every three months but a visit is performed three weeks late, the subsequent visits are shifted three weeks later. When maintenance is completed earlier, the remaining visits can be brought forward.
Impact on visit frequency
Because future dates depend on actual execution, the number of maintenance visits performed during a contract period can differ from the original forecast. This is relevant for contract pricing and may require a commercial arrangement based on the number or type of visits performed.
Operational considerations
After completing a dynamic maintenance visit, the updated forecast should be reviewed before generating additional Service Calls or Service Tasks. This ensures that future work follows the revised maintenance schedule.
Introduction
Meter-Driven Maintenance is a dynamic frequency-based scheduling mechanism that considers equipment usage when determining the next maintenance date. It is suitable for Service Objects whose maintenance requirements depend on running hours, kilometres, production cycles or other measurable usage.
Meters and counters
The Service Object must contain the appropriate meter or counter information, including the primary meter component required by the maintenance schedule. Meter readings are recorded against the relevant component and provide the usage information used for maintenance calculations.
Maintenance calculation
Meter-Driven Maintenance combines the configured calendar frequency with a usage threshold. The system estimates when the threshold will be reached using the available meter readings. If the expected threshold date occurs before the next frequency-based maintenance date, the visit is brought forward. Otherwise, the frequency-based date remains applicable.
Dynamic forecasting
When new meter readings become available, the expected usage and maintenance dates can be recalculated. Changes in equipment usage may therefore result in earlier maintenance visits or changes to the number of visits required during the contract period.
Data quality
Accurate and regular meter readings are essential for reliable forecasting. Incorrect starting values, missing readings or unexpected counter changes can affect the calculated maintenance dates and should be reviewed before operational work is generated.
Introduction
Visit Schedules connect Service Schedules with the Service Objects for which maintenance must be performed. They are commonly created within Contract Proposals or active Service Contracts and determine the planned maintenance obligations for the selected object content.
Creating a Visit Schedule
A Visit Schedule is created by selecting the applicable Service Schedule and entering the rollout start date. The user then selects the Service Objects to which the schedule applies. Where supported, automatic schedule selection can identify eligible schedules based on the configured object and maintenance relationships.
Object selection
The object selection determines which Service Objects are included in the maintenance forecast. This selection must correspond to the intended maintenance scope and, for contract-driven maintenance, the covered contract content.
Forecast options
Additional options can define permitted visit days, working times, calendars and visit-day margins. These conditions influence the calculated planning dates and help align maintenance activities with the customer's operational requirements.
Introduction
Maintenance Forecasting calculates the expected visits based on the selected Service Schedule, Service Objects and scheduling conditions. The forecast provides visibility into future maintenance obligations before they are converted into executable work.
Static visit lines
For static schedules, the Create Lines function generates a preliminary set of visit lines for a reference year. These lines can be reviewed and adjusted before the forecast is created. The user can modify the planned sequence or revisit the schedule settings when the calculated dates do not meet the requirements.
Creating the forecast
The Create Forecast function generates proposed maintenance visits, including planned dates and associated capacity requirements. These visits become visible in the planned maintenance context and can be reviewed before contract promotion or operational rollout.
Dynamic forecasts
Dynamic schedules do not use the same static visit-line preparation. Their forecast depends on the configured maintenance rules and, where applicable, actual realization dates or meter readings. Future visits can change when new operational information becomes available.
Introduction
The Planned Maintenance Overview provides access to forecasted visits and supports the conversion of maintenance obligations into Service Calls and Service Tasks. Planned visits are identified by Visit IDs, allowing users to track which obligations have already resulted in operational work.
Reviewing planned visits
Users can review planned maintenance from the relevant Service Contract or through the periodic planned maintenance sessions. The overview supports filtering by information such as date, Event Code, Service Object, contract and task creation status.
Creating Service Calls and Tasks
When a planned visit becomes due, it can be converted into a Service Call and the associated Service Task. The Event Code determines the task's work package, while the Service Object and applicable contract provide the operational and financial context. Before creating work, the user should confirm that the visit is required and has not already been processed.
Cancelling planned visits
Planned Visit IDs can be cancelled when the corresponding maintenance activity should not be performed. The user should review the resulting maintenance overview to ensure that remaining obligations are still correctly represented.
Introduction
Once planned maintenance has been converted into a Service Call and Service Task, execution follows the standard Service Management process. The Service Task contains the planned work and provides the basis for registering labor, materials, Service Operations and other execution results.
Task execution
The assigned technician performs the maintenance activity and registers the required results against the Service Task. Depending on the Event Code and Object Type, this can include inspections, measurements, component activities, counter readouts and material consumption.
Realization
Completing and realizing the Service Task records the performed work and its associated project transactions. For dynamic maintenance, the actual realization date can also influence the calculation of future visits.
Maintenance history
Completed Service Calls and Service Tasks provide the operational history of maintenance performed on the Service Object. This information supports subsequent maintenance decisions and provides a record of the activities carried out under the applicable contract or maintenance schedule.
Introduction
Planned Service Campaigns support maintenance or service activities that must be performed across a selected group of Service Objects outside the normal recurring contract schedule. Examples include product recalls, technical inspections and one-off service programs.
Campaign scope
The campaign identifies the relevant Service Objects and the work to be performed. Object selection can be based on configured criteria, allowing a defined population of assets to be included in the service activity.
Operational rollout
The selected Service Objects can be used to generate Service Calls and Service Tasks for the required work. The associated Event Code provides the standard work package, helping ensure consistent execution across the selected objects.
Financial processing
Campaign-related work uses the applicable Project Integration and financial configuration. Where the activity is not covered by a Service Contract, its chargeability must be determined through the relevant Service Management and project settings.